Valor: efficient, software-only region conflict exceptions
نویسندگان
چکیده
منابع مشابه
Conflict Exceptions: Providing Simple Parallel Language Semantics with Precise Hardware Exceptions
We argue in this paper that concurrency errors should be treated as exceptions, i.e., have fail-stop behavior and precise semantics. We propose an exception model based on conflict of synchronization-free regions, which precisely detects a broad class of data-races. We show that our exceptions provide enough guarantees to simplify high-level programming language semantics and debugging, but are...
متن کاملCrash-Only Software
Crash-only component has PWR switch: stop=crash clean shutdown loss of power kernel panic cure transient failure Only one way to go down only one way to come up: start = recover Each component must has a PWR switch uniform behavior Crash-only system = assembly of crash-only components; system PWR switch implemented in terms of components' switches PWR switch is external, does not invoke compone...
متن کاملReliability Aware Exceptions for Software Directed Fault Handling
Today reliability emerges as a first order design constraint. Faults encountered in a chip can be classified into three categories: transient, intermittent and permanent. Fault classification allows a chip designer to provide the appropriate corrective action for each fault type. However, fault classification and correction are expensive mechanisms to implement in hardware. In spite of their cr...
متن کاملSoftware-Only Value Speculation Scheduling
Recent research in value prediction, including several recent publications for MICRO, shows a surprising amount of predictability for the values produced by register-writing instructions. Several hardware based value predictor designs have been proposed to exploit this predictability by eliminating flow dependencies for highly predictable values. A hardware and software based technique, value s...
متن کاملReasoning and Improving on Software Resilience against Unanticipated Exceptions
In software, there are the errors anticipated at specification and design time, those encountered at development and testing time, and those that happen in production mode yet never anticipated. In this paper, we aim at reasoning on the ability of software to correctly handle unanticipated exceptions. We propose an algorithm, called short-circuit testing, which injects exceptions during test su...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: ACM SIGPLAN Notices
سال: 2015
ISSN: 0362-1340,1558-1160
DOI: 10.1145/2858965.2814292